Pruning e2e verification - #404
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6df10e3415
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| Message: []byte(msg), | ||
| RequiredEpoch: (*uint64)(&epoch), | ||
| }) | ||
| require.NoErrorf(t, err, "failed to sign message on sidecar %d", i) |
There was a problem hiding this comment.
Retry SignMessage when creating pruning test requests
createPruningRequest performs a single SignMessage call per sidecar and immediately fails on any transient RPC/storage error. This makes the new pruning test flaky under the same transaction-conflict conditions already handled elsewhere in this suite (for example, sign_test.go retries this API). A bounded retry loop here would prevent intermittent CI failures that are unrelated to pruning behavior.
Useful? React with 👍 / 👎.
| RETENTION_SIGNATURE_EPOCHS=${RETENTION_SIGNATURE_EPOCHS:-1000} | ||
| RETENTION_PROOF_EPOCHS=${RETENTION_PROOF_EPOCHS:-1000} | ||
| PRUNER_INTERVAL=${PRUNER_INTERVAL:-1m} | ||
| SYNC_EPOCHS=${SYNC_EPOCHS:-1000} |
There was a problem hiding this comment.
Derive sync epochs from retention defaults
SYNC_EPOCHS defaults to 1000 even when retention is overridden to a much smaller value. With this change, users can now set RETENTION_VALSET_EPOCHS via env, but if they forget to also set SYNC_EPOCHS, the generated config becomes invalid (sync.epochs > retention.valset-epochs) and relay startup fails due to config validation. The default should be capped/derived from retention to avoid this regression when enabling pruning settings.
Useful? React with 👍 / 👎.
🧪 Test Coverage ReportCoverage: |
# Conflicts: # .github/workflows/tests.yaml # e2e/scripts/generate_network.sh
PR Type
Tests, Enhancement
Description
Add pruning end-to-end verification test
Scan
bboltandbadgerstorageParameterize retention, sync, pruner settings
Add CI job and Make target
Diagram Walkthrough
File Walkthrough
3 files
Add pruning end-to-end storage verificationAdd pruning E2E CI matrix jobAdd dedicated pruning E2E target1 files
Extract reusable environment loading helper3 files
Pass pruning settings into generated networkMake sidecar pruning values environment-drivenExport pruning-related environment variables